Is it too much CI @sashahilton00 ?

@Johannesd3 it looks fine. My only concern is whether the tests on the various different systems are run in parallel and ho long they take, not sure how much resource Github grants projects to run CI workloads.

No, that's too much. It's 100 minutes per run, and I think that's 20 runs per month, that's not enough. (I don't know why mac os suddenly failed.)

Github actions is free for public repos, right? It's only private repos that have the 2k monthly limit.

Didn't know that, thx. Another inconvenience: It will take twice as long (15min) until the tests are finished ...

I will try to rebase this PR using the latest changes from dev, and try to fix the macOS problem

The target directory should rather be cached by os + rustc version, but I have no idea how to achieve this.

Anyway, I will close this PR and reopen it, as I want to see how much caching improves the speed.

Any idea why the Run cargo test --workspace step after Run cargo build --workspace --examples does more compilation, including some of the same stuff again? Is that right?

Yes, those #[cfg(test)] blocks are only considered if the tests are executed, but not if the examples are compiled, so every crate needs to be compiled again.

Next try to check caching again, hopefully it's the last try. Sorry for spamming you.

I don't quite understand the macOS error :( Apparently it's caused by caching, but I don't know why.

I reduced the scope of this PR to experiment further with CI without blocking this. I created a PR in my repository (Johannesd3#13) where I can test stuff.